Awesome, thanks, Hiram ! I will look at it ASAP (today, hopefully) ....

btw, do you have any comments on #284, #283 or #285 ? I really want to solve our gordian knot asap, not necessarily by implementing these features (although they would be a solution for the offline use case).

I had a look at the PR:

• The extraction for the maven coordinates is quite smart, like it :)
• However: Dependencies in the Maven assembly are already have the local repository path as source. I guess you had an other use case in mind where you need to find out this path on your own (i.e. not jar dependencies)
• For the artefact of this pom.xml, I think it is not needed to watch the repository variant but the one created in target/ (so that a mvn package would also trigger a rebuild)

Some improvement coming to mind, too:

• We could ignore all non SNAPSHOT dependencies from watching, or ? That would speed up things a bit.
• I injected the local repository directly into the tracker (via a session) so no need to pass it down as argument (done).

I will refactor the PR a bit (have seen some redundant directory name movememnt, too) and merge it into branch integration so we can continue from there on.

I merged the changes in by hand. thanks again.

cool looks good!